Resource-sensitive token-based access point selection

ABSTRACT

Resource-sensitive token-based access point selection is disclosed. A user equipment (UE) can generate a request for resources that can be shared with an selection component remote from the UE. The request for resources can be generated independent of the UE receiving information about an access point (AP) in range of the UE. The selection component can pair the UE with an AP resource based on AP data and UE data. The selection component can generate a token comprising information related to the pairing. The UE can receive the token via a device other than the AP or via the AP. The token can be employed by the UE to initiate a link to the AP to enable use of the AP resource by the UE. The link can be resource sensitive in view of the request for resources and available AP resources.

RELATED APPLICATIONS

This application is a continuation of, and claims priority to, U.S.patent application Ser. No. 16/252,556, filed on 18 Jan. 2019, entitled“RESOURCE-SENSITIVE TOKEN-BASED ACCESS POINT SELECTION”, which is acontinuation of U.S. patent application Ser. No. 14/680,992, filed on 7Apr. 2015, entitled “RESOURCE-SENSITIVE TOKEN-BASED ACCESS POINTSELECTION,” now issued as U.S. Pat. No. 10,225,795. The entirety of theaforementioned application(s) is/are hereby incorporated by referenceherein.

TECHNICAL FIELD

The disclosed subject matter relates to wireless network communication,including resource-sensitive token-based access point selection via awireless network.

BACKGROUND

By way of brief background, conventional access point selectiongenerally employs access points (APs) that are visible to, and broadcastidentification information to, mobile devices. As an example, a Wi-Fiaccess point (AP) can broadcast a service set identifier (SSID). ThisSSID can be received by a mobile device or a user equipment, hereinafter‘UE’ or similar term, to identify a proximate AP. Identification of theAP can enable the UE to link with the AP to allow communication ofinformation across an air interface. As APs become more ubiquitous, thenumber of APs available to a UE can increase dramatically and candecrease the efficiency of AP selection by the UE. More particularly,knowledge of available resources via different APs can lead to lessefficient allocation of resources.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an illustration of an example system that facilitatesresource-sensitive access point selection in accordance with aspects ofthe subject disclosure.

FIG. 2 is a depiction of an example system that facilitatesresource-sensitive access point selection based on UE data received viaan AP component in accordance with aspects of the subject disclosure.

FIG. 3 illustrates an example system that facilitates resource-sensitiveaccess point selection employing a nodal AP controller component inaccordance with aspects of the subject disclosure.

FIG. 4 illustrates an example system that facilitates resource-sensitiveaccess point selection for a plurality of AP components in accordancewith aspects of the subject disclosure.

FIG. 5 illustrates an example method facilitating resource-sensitiveaccess point selection in accordance with aspects of the subjectdisclosure.

FIG. 6 illustrates an example method facilitating resource-sensitiveaccess point selection based on UE data received via an AP component inaccordance with aspects of the subject disclosure.

FIG. 7 depicts an example method facilitating resource-sensitivetoken-based access point selection via a UE component in accordance withaspects of the subject disclosure.

FIG. 8 illustrates an example method facilitating resource-sensitiveaccess point selection for a plurality of AP components in accordancewith aspects of the subject disclosure.

FIG. 9 depicts an example schematic block diagram of a computingenvironment with which the disclosed subject matter can interact.

FIG. 10 illustrates an example block diagram of a computing systemoperable to execute the disclosed systems and methods in accordance withan embodiment.

DETAILED DESCRIPTION

The subject disclosure is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the subject disclosure. It may be evident, however,that the subject disclosure may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to facilitate describing the subjectdisclosure.

Conventional access point (AP) selection generally employs access points(APs) that are visible to, and broadcast identification information to,mobile devices. As an example, a femtocell AP can broadcast anidentifier that can be received by a mobile device or a UE to aid inidentifying the femtocell AP as within range of the UE. Identificationof the AP can enable the UE to link with the AP to allow communicationof information across an air interface, e.g., via cellular, Wi-Fi, nearfield communication (NFC), infrared (IR), Bluetooth, ZigBee, etc. As APsbecome more ubiquitous, the number of APs available in range of a UE canincrease which can decrease the efficiency of AP selection at the UE.Further, lack of knowledge related to available AP resources can lead toless efficient allocation of resources via UE selection of APs with lessideal matches between an available resource characteristic and a UEdesignated resource characteristic. In a further aspect, APs with smallcoverage footprints can result in frequent handovers to other APs for aUE that changes location in time as compared to selection of largerfootprint APs for moving devices to lower handoffs, etc.

The instant disclosure seeks to reduce the effects of conventional APselection technologies. In an aspect, APs can be adapted to receive UEidentifier (UEID) information to enable selection of an AP. Of note,this can be in addition to, or in place of, the AP making AP identifier(APID) information, e.g., SSID, etc., available to a UE. As an example,an AP can be ‘invisible’ by not broadcasting an APID and, rather,receiving UEIDs for UEs proximate to the AP. As another example, an APcan both broadcast an APID and also receive UEIDs. Generally, thebalance of the instant disclosure will focus on invisible APs forclarity and brevity, but all embodiments of APs that are not invisibleare also to be considered within the scope if the present disclosure. Inan aspect, UE data can include UEID information, historical UEinformation, UE location information (e.g., location, proximity, etc.),UE requested resource information (e.g., current resourcecharacteristic, minimum resource characteristic, ideal resourcecharacteristic, anticipated resource characteristic, historical resourcecharacteristic, etc.), UE state information (e.g., charging, idle,active, background apps running, etc.), UE provider information, UEsubscription plan information, UE environmental information, or nearlyany other type of UE related information. In another aspect, AP data caninclude APID information, historical AP information, AP locationinformation, AP available resource information (e.g., currentlyavailable, anticipated available, historically available, whitelists,blacklists, etc.), AP state information, AP carrier information, APenvironmental information, or nearly any other type of AP relatedinformation. Moreover, an AP can include devices or components enablinga communicative link between an AP and a UE, e.g., a Wi-Fi AP,femto/pico/microcell, NodeB, eNodeB, Bluetooth AP, point of sale (POS)component including IR, NFC, or other types of POS AP, etc. In anembodiment, NFC can use electromagnetic induction between two antennaslocated within each other's near field, effectively forming an air-coretransformer. Further, NFC can involve an initiator component and atarget component wherein the initiator component can generates a radiofrequency field that can induce power in the, typically passive, targetcomponent, often referred to as a “NFC tag” This can enable NFC targetcomponents to take very simple form factors such as tags, stickers, keyfobs, cards, etc., often as passive or unpowered devices. A UE cancorrespondingly be a mobile device, smartphone, tablet computer,wearable computing device, smart credit/debit card component, laptop,vehicular computing device, etc.

Where an AP receives UEIDs for proximate UEs, an AP, in an embodiment ofthe instant disclosure, can then select which UEs to link to the AP.Moreover, in an aspect, the AP can determine what resources to makeavailable to the UEs selected for linking. Where the AP is invisible,this can shift aspects of AP selection from a UE to an AP. Where the APselects a UE for linking, deficiencies of conventional AP selectiontechnologies can be mitigated. As an example, selection of a UE by an APcan be processed by non-UE components, e.g., AP components, etc., whichcan improve UE battery consumption, etc., As a further example,selection of a UE by an AP can be cognizant of AP resources allowingallocation of those resources in a more controlled manner. In anotherexample, UE data can be considered to allow selection of a UE by an APin a manner that comports with the usage of the UE, e.g., selection of aUE by larger footprint APs in environments where the UE is more mobile,selection of a UE by smaller footprint APs in environments where the UEis less mobile, selection of a UE by an AP based on the historical useof the UE, etc.

To this end, some embodiments of the disclosed subject matter caninclude generating access token data (ATD) that can enable selection ofa UE-AP pair with regard to forming a communicative link between the UEand the AP. The ATD can be generated in response to receiving UE data.As an example, where UE data includes requested resource minimumcharacteristics and ideal characteristics, the ATD can compriseinformation indicating a AP for the UE to link to that is selected basedon current and anticipated available resources at the AP and their fitto the minimum characteristics and ideal characteristics of the UErequested resource. This example illustrates that resource usageefficiency can be affected by allowing selection of UE-AP pairs thatconsider resource needs and available resources for a given UE set and agiven AP set. In an aspect, the ATD can be received by the UE,particularly where an AP is invisible, via nearly any modality, e.g.,via Wi-Fi, Bluetooth, cellular, LTE, IR, NFC, etc. The ATD can then beemployed by the UE to initiate a link with an AP indicated in the ATD.As such, for example, a UE can broadcast UE data that can be received byan AP to enable generation of ATD which can be received by the UE toenable initiation of a link with an AP indicated in the ATD. In someinstances, no AP can be indicated, e.g., in instances where there UEresource requirements cannot be met by an available AP, etc., in whichcase no ATD may be generated, an ATD indicating no appropriate APs areavailable can be generated, etc.

In an embodiment, an AP can generate ATD. Where an AP receives UE datafor one or more UEs in range of the AP, the AP can select which UEs tolink with and can generate ATD reflecting this selection. In an aspect,selection can consider requested resources, available resources,carriers, UE preference data, black/white listed UEIDs, etc. As such,even though the AP can be invisible to UEs proximate to the AP, the APcan receive and employ UE data to select UE-AP pairs. This selection canbe reflected in ATD. ATD can be received by the UE to enable linkingwith a designated AP. Where the AP is invisible, linking can occurwithout the UE ‘seeing’ the AP, e.g., via an open broadcast of an SSID,etc. In an aspect, ATD can be received by the UE via nearly anymodality, for example, ATD can be received by the UE via a cellulartransmission to enable linking with a Wi-Fi AP. Of note, in someembodiments, ATD can be included in background transmissions to a UE,e.g., communications not specifically initiated to communicate ATD, forexample, when a UE experiences a handover between cellular sectors,updated ATD can be transmitted to the UE as part of other communicationsto the UE associated with the cellular handover, etc. In otherembodiments, ATD can be part of a ATD-message to the UE, e.g., the ATDcan be comprised in communications to the UE specifically associatedwith communicating ATD.

In an embodiment, a system can comprise a process or memory allowingexecution of stored instructions to enable the processor to receive arequest for resource allocation associated with a user equipment. Therequest for resource allocation can be received from the user equipmentindependent of the user equipment having received information about anaccess point device in advance of the request for resource allocationhaving been received, e.g., the access point can effectively be treatedas invisible to the user equipment. The processor can further determinea fitness metric value related to provisioning a resource via the accesspoint device, and provision the resource for utilization by the userequipment via the access point device, based on the fitness metricvalue. Moreover, the processor can enable access by the user equipmentto the resource via the access point device in response to theprovisioning of the resource.

In another embodiment, a method can comprise receiving, by a systemcomprising a processor, user equipment data associated with a userequipment. The user equipment data can further comprise an indication ofa requested wireless communication resource. The user equipment data canbe received from the user equipment independent of the user equipmenthaving received access point data related to an access point device. Themethod can further comprise determining pair information, by the systemand based on the user equipment data and the access point data, that canbe related to pairing of the user equipment and an access pointresource. Moreover, the method can comprise the system generating accesstoken data associated with an access token based on the user equipmentdata, the access point data, and the pair information. The access tokendata can enable the user equipment to initiate a wireless link to theaccess point device to employ the access point resource.

In a further embodiment, a computer readable medium can compriseinstructions that can cause a system comprising a processor to receivean indication of wireless communication resource needs associated with auser equipment. The indication can be received from the user equipmentindependent of the user equipment receiving access point data related toan access point device. The instructions can also cause the processor todetermine pair information related to pairing of the user equipment andan access point device to enable the user equipment to employ a resourceof the access point device, based on the indication and the access pointdata. Moreover, the instructions can cause the processor to generateresource data associated with enabling the user equipment to initiate awireless link to the access point device to employ the access pointresource and allow access to the resource data by the UE.

To the accomplishment of the foregoing and related ends, the disclosedsubject matter, then, comprises one or more of the features hereinaftermore fully described. The following description and the annexed drawingsset forth in detail certain illustrative aspects of the subject matter.However, these aspects are indicative of but a few of the various waysin which the principles of the subject matter can be employed. Otheraspects, advantages and novel features of the disclosed subject matterwill become apparent from the following detailed description whenconsidered in conjunction with the provided drawings.

FIG. 1 is an illustration of a system 100, which facilitatesresource-sensitive access point selection in accordance with aspects ofthe subject disclosure. System 100 can include access point (AP)component 110. In some embodiments, AP component 110 can be invisible,e.g., AP component 110 can receive UE identifier (UEID) information froma UE rather than transmit AP identifier (APID) information to a UE. Inother embodiments, AP component 110 can both receive UEID informationfrom a UE and transmit APID information to a UE. UE data 120 cancomprise UEID information.

In an aspect, AP component 110 can be comprised in an AP device, e.g., aWi-Fi AP device, a POS device, a femto-, a pico-, or a nano-cell device,a Bluetooth AP device, etc. The AP device can generally facilitatewireless devices, e.g., UEs, etc., to connect to a wired network orother wireless network. An AP can connect to a router as a standalonedevice, but it can also be an integral component of the router or otherdevice itself. Of note, an AP is expressly not restricted to Wi-Fi orIEEE 802.xx-type standards and can encompass other wireless standards,both electromagnetic and non-electromagnetic, such as Bluetooth, Zigbee,IR, etc. As such, an AP, as employed in this disclosure, can be a Wi-Fiaccess point, a POS device employing NFC technology, a Bluetooth AP,etc. As an example, a Wi-Fi AP device can comprise AP component 110 thatcan receive UE data 120 comprising UEID information, can select to linkwith the UE based on UE data 120, and can generate access token data(ATD) 130 to facilitate the UE initiating a link to the Wi-Fi AP device.ATD data can be received by a UE via communications from the Wi-Fi APdevice, e.g., via Wi-Fi or other communication modality embodied in theWi-Fi AP device, or can received by the UE via another component (notillustrated), such as through a cellular communication via a NodeB,wherein ATD 130 can be communicated to the NodeB by a backend networkthat is not illustrated for clarity and brevity.

AP component 110 can receive UE data 120. UE data 120 can include UEIDinformation, historical UE information, UE location information (e.g.,location, proximity, etc.), UE requested resource information (e.g.,current resource characteristic, minimum resource characteristic, idealresource characteristic, anticipated resource characteristic, historicalresource characteristic, etc.), UE state information (e.g., charging,idle, active, background apps running, etc.), UE provider information,UE subscription plan information, UE environmental information, ornearly any other type of UE related information. In an aspect, UE data120 can function to bring into AP component 110 data relevant toselecting a UE-AP pair. Selection of a UE-AP pair can be related toseeking to pair a UE and an AP in a manner that reduced waste ofresources. As an example, where UE data 120 comprises informationindicating that resources for communicating transactional data, which isrelatively compact and brief in comparison to streaming data or thelike, is desired, an AP can be selected to be paired to the UE where theAP has an available resource that will facilitate the communication ofthe transactional data but cannot select an AP that does not haveadequate resources or that has a resource that would be better employedby another UE that can request a high bandwidth resource. As such,selection can facilitate improved allocation of resources available viaan AP for UE use in consideration of requested provisioning of aresource by the UE. In a scenario where the AP is invisible, this canallow AP component 110 to drive AP selection via ATD 130 as initiated bythe UE.

In some embodiments, UE data 120 can comprise information for multipleUEs, such that selection of UE-AP pairs via AP component 110 results inallocation of resources to the several UEs in a manner that reduceswaste of the resources. As an example, a low bandwidth connection with afirst UE can be indicated in ATD 130, such as a connection on a crowdedfrequency of an AP device, where the first UE needs minimal bandwidth,while a second UE can be allocated a connection via ATD 130 for arelatively uncrowded frequency channel of the AP device where the secondUE requests a high bandwidth channel, e.g., for streaming video, etc.

In other embodiments, AP comp 110 can select a UE-AP pairing from amonga plurality of AP devices via ATD 130. AP component 110 can receiveinformation related to resources available for a plurality of APdevices, not illustrated in FIG. 1 for clarity and brevity. AP component110 can then select which resource on which AP device to select for agiven UE requested resource, e.g., information contained in UE data 120.As such, rather than simply selecting an AP with the strongest signal asmight be done in a conventional technique, the instant disclosure canallow for selection of an AP based on matching an available resourcewith a requested resource, e.g., an AP that would otherwise have a lowersignal strength can be selected for pairing, via ATD 130, where theresource need and availability are a better match than for an AP thatwould otherwise have a stronger signal strength. Of note, otherconsiderations can also be considered, for example, where there islittle congestion of the wireless networks for several APs andassociated UEs, more bandwidth, higher signal strength, etc., can beselected for a UE-AP pairing. As an example, a high bandwidth APresource can be paired to a UE with a low bandwidth request, even wherethis results in some waste, because it can provide an improved customerexperience and there are not other demands for the same resource.

ATD 130 can comprise information enabling a UE to initiate acommunicative link with a selected AP. The communicative link with theAP can be directed to a designated resource of the AP. The communicativelink with the AP can be responsive to requested resource characteristicsthat can be indicated via UE data 120 to AP component 110. In an aspect,ATD 130 can enable resource-sensitive selection of a UE-AP pair withregard to forming a communicative link between the UE and the AP. ATD130 can be generated by AP component 110. In some embodiments, ATD 130can be received by a UE via AP component 110. In other embodiments, ATD130 can be received by a UE via another component, for example, ATD 130can be communicated to a UE from AP component 110 via a carrier backbonenetwork, through a carrier-side component, over the internet to a 3^(rd)party component, to femtocell, then to the UE through a Bluetoothconnection to the UE.

In an aspect, ATD 130 can comprise UE data 120, in whole or in part. Insome embodiments, ATD 130 can comprise UEID information. Further, ATD130 can comprise AP data, in whole or in part. Moreover, ATD 130 cancomprise information related to a selected UE-AP pairing. In someembodiments, ATD 130 can comprise information related to a plurality ofUE-AP pairings, which can comprise parings for a UE with different APs,parings for a UE with different resources of an AP, parings for aplurality of UEs with different APs, parings for a plurality of UEs withdifferent resources of an AP, no paring for a UE with an AP or APresource, etc. As such, ATD 130 can be generated by AP component 110 tofunction with one UE and one AP device, for multiple UEs and one APdevice, for one UE and multiple AP devices, etc., wherein the APdevice(s) can have one or more resources, the UE(s) can be associatedwith one or more requested resource, and wherein a rule related toselecting an AP resource in response to a UE requested resource has beensatisfied.

FIG. 2 is a depiction of a system 200 that can facilitateresource-sensitive access point selection based on UE data 220 receivedvia AP component 210 in accordance with aspects of the subjectdisclosure. System 200 can include AP component 210. In someembodiments, AP component 210 can be invisible, e.g., AP component 210can receive UEID information from a UE (not illustrated) rather thantransmit APID information to the UE. In other embodiments, AP component210 can both receive UEID information from a UE and transmit APIDinformation to a UE. UE data 220 can comprise UEID information. In anaspect, AP component 210 can be comprised in an AP device. The AP devicecan generally facilitate wireless device connections to a wired networkor other wireless network.

AP component 210 can receive UE data 220. UE data 220 can include UEIDinformation, historical UE information, UE location information, UErequested resource information, UE state information, UE providerinformation, UE subscription plan information, UE environmentalinformation, or nearly any other type of UE related information. In anaspect, UE data 220 can comprise data relevant to selecting a UE-APpair. Selection of a UE-AP pair can be related to pairing a UE and an APin a manner that reduces resource waste. As an example, where UE data220 comprises information indicating that resources for communicatingdata should be highly secure, such as for communicating banking data, anAP can be selected to be paired to the UE where the AP has an availableresource that will facilitate highly secure communication oftransactional information over selecting an AP resource that is of lowersecurity. As such, selection can facilitate improved allocation ofresources available via an AP for UE use in consideration of requestedprovisioning of a resource by the UE. In this example, provisioning ofthe highly secure resource for a UE requesting a highly secure resourceillustrates less waste than pairing another UE not requesting a highlysecure resource, where there the highly secure resource is a limitedresource. Of note, where all resources of the example AP are highlysecure, this selection criteria can be considered moot, and selectioncan be based on other characteristics of the available resources andrequested resources. In some embodiments, UE data 220 can compriseinformation for multiple UEs, such that selection of UE-AP pairs resultsin allocation of resources to the several UEs in a manner that reduceswaste of the resources.

System 200 can comprise selection component 240 that can becommunicatively coupled to AP component 210. Selection comp 240 canselect a UE-AP pairing from among a plurality of AP devices and cangenerate ATD 230 comprising this pairing information. Selectioncomponent 240 can receive information related to resources available fora plurality of AP devices, not illustrated in FIG. 2 for clarity andbrevity, wherein an AP device of the plurality comprises AP component210. Selection component 240 can then select which resource on which APdevice to select for a given UE requested resource, e.g., informationcontained in UE data 220 and received at selection component 240 via APcomponent 210. As such, the instant disclosure can allow for selectionof an AP resource based on a rule related to selection of an availableresource in view of information related to a requested resource.

In some embodiments, selection component 240 can be located remotelyfrom AP component 210. As an example, AP component 210 can be located atan edge device for a radio access network (RAN) while selectioncomponent 240 can be located in a carrier-core component and becommunicatively coupled to AP component 210 via one or more wired and/orwireless links. This aspect of the disclosed subject matter can allowcentralization of selection component 240. In some embodiments,selection component 240 can serve a plurality of AP components. Thisplurality of AP components can, in an aspect, be viewed as ‘remote radioheads’ or ‘thin AP components’, e.g., where AP component 210 embodiesLayer 1 functionality and Layer 2-7 can be embodied and/or virtualizedat selection component 240. In an embodiment, therefore, selectioncomponent 240 can act as Layer 2-7 for a plurality of ‘remote radioheads’ each comprising an AP component 210 that embodies Layer 1functionality. Selection component 240 can generate ATD 230 for anynumber of UE-AP pair selections based on UE data 220.

In other embodiments, selection component 240 can be located local to APcomponent 210. As an example, selection component 240 can be located ina central office in a mall and can interact with AP components locatedwith AP devices in various shops comprising the mall. Selectioncomponent 240 and the several AP components can be communicativelycoupled via a wired and/or wireless local area network associated withthe mall. In some embodiments, selection component 240 can be co-locatedwith AP component 210, for example, where selection component isco-located in an AP device with AP component 210. In some of theseembodiments, selection component 240 can also be communicatively coupledwith other AP components located locally or remotely, e.g., where afirst AP device comprises AP component 210 and selection component 240,selection component 240 can further be coupled to another AP component210 located somewhere else in the mall and/or can be further coupled toanother AP component 210 located in another city/country/etc.

ATD 230 can comprise information enabling a UE to initiate a communicatelink between an AP and the UE, wherein the AP is selected via selectioncomponent 240. The communicative link between the UE and the AP cancomprise a designated resource of the AP. The communicative link withthe AP can be responsive to requested resource characteristics that canbe comprised in UE data 220 and can be passed to selection component 240via AP component 210. In an aspect, ATD 230 can enableresource-sensitive selection of a UE-AP resource pair with regard toforming a communicative link between the UE and the AP. ATD 230 can begenerated by selection component 240. In some embodiments, ATD 230generated by selection component 240 can be received by a UE, notillustrated, via AP component 210, e.g., selection component 240 cangenerate ATD 230 and send it back through AP component 210 to a UE. Inother embodiments, ATD 230 can be received by a UE via anothercomponent, for example, ATD 230 can be communicated to a UE fromselection component 240 via an internet component, a carrier-sidecomponent, etc.

In an aspect, ATD 230 can comprise UE data 220, in whole or in part. Insome embodiments, ATD 230 can comprise UEID information. Further, ATD230 can comprise AP data, in whole or in part. Moreover, ATD 230 cancomprise information related to a selected UE-AP resource pairing. Insome embodiments, ATD 230 can comprise information related to aplurality of UE-AP resource pairings, which can comprise resourceparings for a UE with different APs, parings for a UE with differentresources of an AP, parings for a plurality of UEs with different APs,parings for a plurality of UEs with a different resources of an AP, noparing for a UE with an AP or AP resource, etc. As such, ATD 230 can begenerated for one UE and one AP device, for multiple UEs and one APdevice, for one UE and multiple AP devices, etc., wherein the APdevice(s) can have one or more resources, the UE(s) can be associatedwith one or more requested resource, and wherein a rule related toselecting an AP resource in response to a UE requested resource has beensatisfied.

FIG. 3 illustrates a system 300 that facilitates resource-sensitiveaccess point selection employing nodal AP controller component 350 inaccordance with aspects of the subject disclosure. System 300 caninclude AP component 310. In some embodiments, AP component 310 can beinvisible, e.g., AP component 310 can receive UE data 320 from a UE (notillustrated) rather than transmit AP data (not illustrated) to the UE.In other embodiments, AP component 310 can both receive UE data 320 froma UE and transmit AP data to a UE. In an aspect, AP component 310 can becomprised in an AP device. The AP device can generally facilitatewireless device connections for a UE to a wired network or otherwireless network.

AP component 310 can receive UE data 320. UE data 320 can include UEIDinformation, historical UE information, UE location information, UErequested resource information, UE state information, UE providerinformation, UE subscription plan information, UE environmentalinformation, or nearly any other type of UE related information. In anaspect, UE data 320 can comprise data relevant to selecting a UE-APresource pair. Selection of a UE-AP resource pair can be related topairing a UE and an AP resource in a manner that reduces waste of the APresource. As an example, where UE data 320 comprises informationindicating that resources for communicating data should employ onlyresources having servers in a particular country, an AP resource can beselected to be paired to the UE where the AP has an available resourcethat only employs servers in the indicated country. As such, selectioncan facilitate improved allocation of resources available via an AP forUE use in consideration of requested provisioning of a resource by theUE. Of note, resource selection can be based on other characteristics ofthe available resources and requested resources. In some embodiments, UEdata 320 can comprise information for multiple UEs, such that selectionof UE-AP resource pairs results in allocation of resources to theseveral UEs in a manner that reduces waste of the aggregate resources,e.g., by applying a rule related to the aggregate resources than byrules to individual resources. This can allow for selections that can bewasteful of individual resources while it reduces waste of the aggregateresources.

System 300 can comprise selection component 340 that can becommunicatively coupled to AP component 310 via nodal AP comptrollercomponent 350 and wired and/or wireless network 390, hereinafter‘network 390’. Selection comp 340 can select a UE-AP pairing from amonga plurality of AP devices coupled to nodal AP controller component 350via network 390, although for the sake of clarity and brevity, only APcomponent 310 is illustrated as coupled to nodal AP controller component350 via network 390. Nodal AP controller component 350 can generate ATD330 comprising pairing information. Selection component 340 can receiveinformation related to resources available for a plurality of APdevices, wherein an AP device of the plurality comprises AP component310. Selection component 340 can then select which resource on which APdevice to select for a given UE requested resource, e.g., informationcontained in UE data 320 and received at selection component 340. Assuch, the instant disclosure can allow for selection of an AP resourcebased on a rule related to selection of an available resource in view ofinformation related to a requested resource.

In some embodiments, nodal AP controller component 350 can be locatedremotely from AP component 310. As an example, AP component 310 can belocated in a first country while nodal AP controller component 350 canbe located in a second country and be communicatively coupled to APcomponent 310 via network 390 This aspect of the disclosed subjectmatter can allow centralization of nodal AP controller component 350. Insome embodiments, nodal AP controller component 350 can serve aplurality of AP components. This plurality of AP components can, in anaspect, be viewed as ‘remote radio heads’ or ‘thin AP components’, e.g.,where AP component 310 embodies Layer 1 functionality and Layer 2-7 canbe embodied and/or virtualized at nodal AP controller component 350,while selection functions are performed by selection component 340. Inan embodiment, therefore, nodal AP controller component 350 can act asLayer 2-7 for a plurality of ‘remote radio heads’ each comprising an APcomponent 310 that embodies Layer 1 functionality. Nodal AP controllercomponent 350 can, via selection component 340, generate ATD 330 for anynumber of UE-AP pair selections based on information comprised in UEdata 320.

In other embodiments, nodal AP controller component 350 can be locatedlocal to AP component 310. As an example, nodal AP controller component350 can be located onsite at a retailer and can interact with APcomponents located with POS devices at the various checkout stations ofthe retailer site. Nodal AP controller component 350 and the several APcomponents can be communicatively coupled via a local area networkassociated with the retail site, e.g., network 390. In some embodiments,nodal AP controller component 350 can be co-located with an AP component310, for example, where selection component is co-located in a POSdevice with AP component 310. In some of these embodiments, nodal APcontroller component 350 can also be communicatively coupled with otherAP components located locally or remotely, e.g., where a first POSdevice comprises AP component 310 and nodal AP controller component 350,nodal AP controller component 350 can further be coupled to another APcomponent 310 located somewhere else on the retail site and/or can befurther coupled to another AP component 310 located at another retailsite.

ATD 330 can comprise information enabling a UE to initiate acommunicative link between an AP resource and the UE, wherein the APresource is selected via selection component 340. The communicative linkbetween the UE and the AP can comprise a designated resource of the AP.The communicative link with the AP can be responsive to requestedresource characteristics that can be comprised in UE data 320, whichcharacteristics can be communicated to selection component 340. In anaspect, ATD 330 can enable resource-sensitive selection of a UE-APresource pair with regard to forming a communicative link between the UEand the AP device. ATD 330 can be generated by nodal AP controllercomponent 350, via selection component 340. In some embodiments, ATD 330generated by nodal AP controller component 350 can be received by a UE,not illustrated, via AP component 310, e.g., nodal AP controllercomponent 350 can generate ATD 330 and send it back through AP component310 to a UE. In other embodiments, ATD 330 can be received by a UE viaanother component, for example, ATD 330 can be communicated to a UE fromnodal AP controller component 350 via an internet component, acarrier-side component, etc.

In an aspect, ATD 330 can comprise UE data 320, in whole or in part. Insome embodiments, ATD 330 can comprise UEID information. Further, ATD330 can comprise AP data, in whole or in part. Moreover, ATD 330 cancomprise information related to a selected UE-AP resource pairing. Insome embodiments, ATD 330 can comprise information related to aplurality of UE-AP resource pairings, which can comprise resourceparings for a UE with different APs, parings for a UE with differentresources of an AP, parings for a plurality of UEs with different APs,parings for a plurality of UEs with a different resources of an AP, noparing for a UE with an AP or AP resource, etc. As such, ATD 330 can begenerated for one UE and one AP device, for multiple UEs and one APdevice, for one UE and multiple AP devices, etc., wherein the APdevice(s) can have one or more resources, the UE(s) can be associatedwith one or more requested resource, and wherein a rule related toselecting an AP resource in response to a UE requested resource has beensatisfied.

FIG. 4 illustrates a system 400 that facilitates resource-sensitiveaccess point selection for a plurality of AP components, 410-414, inaccordance with aspects of the subject disclosure. System 400 caninclude AP component 410, AP component 412, and AP component 414. Insome embodiments, one or more of AP component(s) 410-414 can beinvisible, e.g., AP component(s) 410-414 can receive UE data from UE(s)420-424 rather than transmit AP data (not illustrated) to UE(s) 420-424.In other embodiments, AP component(s) 410-414 can both receive UE datafrom UE(s) 420-424 and transmit AP data to UE(s) 420-424. In an aspect,AP component(s) 410-414 can be comprised in AP device(s), notillustrated. The AP device(s) can generally facilitate wireless deviceconnections for UE(s) 420-424 to a wired network or other wirelessnetwork, e.g., network 490.

AP component(s) 410-414 can receive UE data from UE(s) 420-424. UE datacan include UEID information, historical UE information, UE locationinformation, UE requested resource information, UE state information, UEprovider information, UE subscription plan information, UE environmentalinformation, or nearly any other type of UE related information. In anaspect, UE data can comprise data relevant to selecting a UE-AP resourcepair. Selection of a UE-AP resource pair can be related to pairing a UEand an AP resource in a manner that reduces waste of the AP resource. Asan example, where UE data comprises information indicating thatresources for communicating data should employ only resources of a setof carriers, an AP resource can be selected to be paired to the UE wherethe AP has an available resource that is of the set of carriers. Assuch, selection can facilitate improved allocation of resourcesavailable via an AP for UE use in consideration of requestedprovisioning of a resource by UE(s) 420-424. Of note, resource selectioncan be based on other characteristics of the available resources andrequested resources. In some embodiments, UE data can compriseinformation for multiple UEs, e.g., UE(s) 420-424, such that selectionof UE-AP resource pairs results in allocation of resources to theseveral UEs in a manner that reduces waste of the resources.

System 400 can comprise selection component 440 that can becommunicatively coupled to AP component(s) 410-414 via nodal APcomptroller component 450 and wired and/or wireless network 490.Selection comp 440 can select a UE-AP pairing from among a plurality ofAP devices coupled to nodal AP controller component 450 via network 490,e.g., AP devices comprising AP component(s) 410-414 as illustrated.Nodal AP controller component 450 can generate ATD comprising pairinginformation, e.g., first toke data 430 (hereinafter token 430), secondtoken data 432 (hereinafter token 432), and/or third token data 434(hereinafter token 434). Selection component 440 can receive informationrelated to resources available for a plurality of AP devices,correspondingly comprising AP component(s) 410-414. Selection component440 can then select which resource on which AP device to select for agiven UE requested resource, e.g., information contained in UE data fromUE(s) 420-424 and received at selection component 440. As such, theinstant disclosure can allow for selection of an AP resource based on arule related to selection of an available resource in view ofinformation related to a requested resource.

System 400 illustrates that first AP component 410 (hereinafter AP 410)and second AP component 412 (hereinafter AP 412) can receive UE datafrom UE 420. Further illustrated, AP 410, AP 412, and third AP component(hereinafter AP 414) can receive UE data from UE 422. Additionallydepicted, AP 412 and AP can receive UE data from UE 424. As such, viacommunication over network 490, nodal AP controller component 450 canreceive UE data for UE 420 from AP 410 and AP 412, other UE data for UE422 from AP 410, AP 412, and AP 414, and additional UE data for UE 424from AP 412 and AP 414. Additionally, nodal AP controller component 450can receive AP data for AP 410, AP 412 and AP 414. Selection component440 can then employ this UE data and AP data to select UE-AP resourcepairs for UE(s) 420-424 and AP resources correspondingly associated withAP 410-414. In an aspect, AP resources associated with AP 414 would notbe allocated to UE 420 because AP 414 is out of range of, UE 420.Similarly, AP resources associated with AP 410 would not be allocated toUE 424 because AP 410 is out of range of, UE 424. Moreover, AP resourcesassociated with APs 410-414 could be allocated to UE 422 because APs410-414 are all in range of, UE 422.

In some embodiments, nodal AP controller component 450 can be locatedremotely from one or more of AP components 410-414. As an example, APcomponent 410 can be located in a first city, AP components 412-414 canbe located in a second city, and nodal AP controller component 450 canbe located in a third city and be communicatively coupled to APcomponents 410-414 via network 490 This aspect of the disclosed subjectmatter can allow centralization of nodal AP controller component 450. APcomponents 410-414 can, in an aspect, be viewed as ‘remote radio heads’or ‘thin AP components’, e.g., where AP components 410-414 each embodyLayer 1 functionality, Layers 2-7 can be embodied and/or virtualized atnodal AP controller component 450. In an embodiment, therefore, nodal APcontroller component 450 can act as Layer 2-7 for a plurality of ‘remoteradio heads,’ e.g., AP components 410-414. Nodal AP controller component450 can, via selection component 440, generate ATD 430 for any number ofUE-AP pair selections based on information comprised in UE data 420 andAP data, not illustrated for brevity.

In other embodiments, nodal AP controller component 450 can be locatedlocal to an AP component, e.g., AP component(s) 410-414. As an example,nodal AP controller component 450 can be located at a campus server andcan interact with AP components 410-414 located at various campusbuildings and coupled to AP devices in the various classrooms of thecampus buildings. Nodal AP controller component 450 and the APcomponents 410-414 can be communicatively coupled via a campus LAN,e.g., network 490. In some embodiments, nodal AP controller component450 can be co-located with an AP component, e.g., 410-414. In some ofthese embodiments, nodal AP controller component 450 can also becommunicatively coupled with other AP components located locally orremotely, e.g., where AP component 410 is local to nodal AP controllercomponent 450, nodal AP controller component 450 can further be coupledto another AP component, e.g., 412-414 located, for example, at a branchcampus facility, etc.

Token(s) 430-434 can comprise information enabling a UE, e.g., UE(s)420-424, to initiate a communicative link between an AP resource and theUE, wherein the AP resource is selected via selection component 440. Thecommunicative link between the UE and the AP device can comprise adesignated resource of the AP. The communicative link with the AP devicecan be responsive to requested resource characteristics that can becomprised in UE data, e.g., from UE 420-424, which characteristics canbe communicated to selection component 440. In an aspect, Token(s)430-434 can enable resource-sensitive selection of a UE-AP resource pairwith regard to forming a communicative link between UE(s) 420-424 andcorresponding AP device(s). Token(s) 430-434 can be generated by nodalAP controller component 450, via selection component 440. In someembodiments, Token(s) 430-434 generated by nodal AP controller component450 can be received by UE(s) 420-424 via corresponding AP component(s)410-414, e.g., nodal AP controller component 450 can generate token(s)430-434 and send them back through AP component(s) 410-414 to UE(s)420-424. In other embodiments, token(s) 430-434 can be received by UE(s)420-424 via another component, for example, token(s) 430-434 can becommunicated to UE(s) 420-424 from nodal AP controller component 450 viaan internet component, a carrier-side component, etc.

In an aspect, token(s) 430-434 can comprise UE data, in whole or inpart. In some embodiments, token(s) 430-434 can comprise UEIDinformation. Further, token(s) 430-434 can comprise AP data, in whole orin part. Moreover, token(s) 430-434 can comprise information related toa selected UE-AP resource pairing. In some embodiments, token(s) 430-434can comprise information related to a plurality of UE-AP resourcepairings, which can comprise resource parings for UE(s) 420-424 withdifferent APs, parings for UE(s) 420-424 with different resources of anAP, parings for a plurality of UEs 420-424 with different APs, paringsfor a plurality of UEs 420-424 with different resources of an AP, noparing for UE(s) 420-424 with an AP or AP resource, etc. As such,token(s) 430-434 can be generated for one UE (e.g., from UE 420-424) andone AP device, for multiple UEs 420-424 and one AP device, for one UEand multiple AP devices, etc., wherein the AP device(s) can have one ormore resources, the UE(s) 420-424 can be associated with one or morerequested resource, and wherein a rule related to selecting an APresource in response to a UE requested resource has been satisfied. Ofnote, in some embodiments, where token 430 comprises UE-AP pairinformation for the several UEs 420-424, tokens 432-434 may not begenerated, e.g., each of UEs 420-424 can receive token 430 having allthe pairing info needed. In other embodiments, token(s) 430-434 cancomprise UE-AP resource pairing info for specific UE(s) 420-424 suchthat each UE receives a corresponding token with pairing info specificto that UE.

In view of the example system(s) described above, example method(s) thatcan be implemented in accordance with the disclosed subject matter canbe better appreciated with reference to flowcharts in FIG. 5 -FIG. 8 .For purposes of simplicity of explanation, example methods disclosedherein are presented and described as a series of acts; however, it isto be understood and appreciated that the claimed subject matter is notlimited by the order of acts, as some acts may occur in different ordersand/or concurrently with other acts from that shown and describedherein. For example, one or more example methods disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methods. Furthermore,not all illustrated acts may be required to implement a describedexample method in accordance with the subject specification. Furtheryet, two or more of the disclosed example methods can be implemented incombination with each other, to accomplish one or more aspects hereindescribed. It should be further appreciated that the example methodsdisclosed throughout the subject specification are capable of beingstored on an article of manufacture (e.g., a computer-readable medium)to allow transporting and transferring such methods to computers forexecution, and thus implementation, by a processor or for storage in amemory.

FIG. 5 illustrates a method 500 facilitating resource-sensitive accesspoint selection in accordance with aspects of the subject disclosure. At510, method 500 can include receiving user equipment (UE) data. UE datacan include UEID information, historical UE information, UE locationinformation (e.g., location, proximity, etc.), UE requested resourceinformation (e.g., current resource characteristic, minimum resourcecharacteristic, ideal resource characteristic, anticipated resourcecharacteristic, historical resource characteristic, etc.), UE stateinformation (e.g., charging, idle, active, background apps running,etc.), UE provider information, UE subscription plan information, UEenvironmental information, or nearly any other type of UE relatedinformation. UE data can be employed with AP data to select a UE-APpair, wherein AP data can include APID information, historical APinformation, AP location information, AP available resource information(e.g., currently available, anticipated available, historicallyavailable, whitelists, blacklists, etc.), AP state information, APcarrier information, AP environmental information, or nearly any othertype of AP related information. An AP can include devices or componentsenabling a communicative link between an AP component and a UEcomponent, e.g., a Wi-Fi AP, femto/pico/microcell, NodeB, eNodeB,Bluetooth AP, point of sale (POS) component including IR, NFC, or othertypes of POS AP, etc. A UE can correspondingly be a mobile device,smartphone, tablet computer, wearable computing device, smartcredit/debit card component, laptop, vehicular computing device, etc.

At 520, method 500 can comprise, determining resource allocation basedon the UE data received at 510. Determining resource allocation cancomprise applying a rule related to selection of a resource, e.g., an APresource, in view of characteristics of the resource requested by a UEand characteristics of a resource that is available via an AP. In anaspect, the rule can consider current, historical, and/or anticipatedresource characteristics. As an example, historical information for anAP resource can indicate that the resource is associated with strongencryption of communicated data, which can be considered in view of anyrequest for an encrypted resource from a UE. As another example, an APresource can be anticipated to be available through a designated time,such as where a maintenance schedule indicates that the AP resource willbe unavailable after the time for maintenance. This anticipated servicewindow can be employed in selecting an appropriate UE-AP pairing. Nearlyany other historical characteristic and/or anticipated futurecharacteristic for an AP resource can be employed in the determiningresource allocation of 520, and all such characteristics are consideredwithin the scope of the present disclosure. Moreover, similarapplication of historical and anticipated characteristics of UErequested resources can be similarly employed. As an example, where a UEhistorically follows a pattern of resource usage, such as low bandwidthusage between 8 am and 9 am and then high bandwidth usage from 9 am to10 am when the UE is located at location X, this historical informationcan be employed to anticipate future UE resource request characteristicsbased on time an d location such that an appropriate UE-AP resource paircan be designated in conjunction with the UE location and time.

At 530, method 500 can comprise, generating access token data (ATD) thatcan enable selection of a UE-AP pair with regard to forming acommunicative link between a UE and an AP component. At this point,method 500 can end. ATD can comprise information enabling a UE toinitiate a communicative link with a selected AP. The communicative linkwith the AP can be directed to a designated resource of the AP. Thecommunicative link with the AP can be responsive to requested resourcecharacteristics that can be indicated via UE data. In an aspect, ATD canenable resource-sensitive selection of a UE-AP pair with regard toforming a communicative link between the UE and the AP. In someembodiments, ATD can be received by a UE via an AP component. In otherembodiments, ATD can be received by a UE via another component, forexample, ATD can be communicated to a UE from via a carrier backbonenetwork to the UE, etc. In an aspect, ATD can comprise UE data, in wholeor in part. In some embodiments, ATD can comprise UEID information.Further, ATD can comprise AP data, in whole or in part. Moreover, ATDcan comprise information related to a selected UE-AP pairing. In someembodiments, ATD can comprise information related to a plurality ofUE-AP pairings, which can comprise parings for a UE with different APs,parings for a UE with different resources of an AP, parings for aplurality of UEs with different APs, parings for a plurality of UEs withdifferent resources of an AP, no paring for a UE with an AP or APresource, etc. As such, ATD can be generated for one UE and one APdevice, for multiple UEs and one AP device, for one UE and multiple APdevices, etc., wherein the AP device(s) can have one or more resources,the UE(s) can be associated with one or more requested resource, andwherein a rule related to selecting an AP resource in response to a UErequested resource has been satisfied.

FIG. 6 illustrates a method 600 facilitating resource-sensitive accesspoint selection based on UE data received via an AP component inaccordance with aspects of the subject disclosure. At 610, method 600can include receiving UE data at a selection component via an accesspoint component. The selection component can be located remotely fromthe access point component. UE data can include UEID information,historical UE information, UE location information, UE requestedresource information, UE state information, UE provider information, UEsubscription plan information, UE environmental information, or nearlyany other type of UE related information. The UE data can be employedwith AP data to select a UE-AP pair, wherein AP data can include APIDinformation, historical AP information, AP location information, APavailable resource information, AP state information, AP carrierinformation, AP environmental information, or nearly any other type ofAP related information. An AP can include devices or components enablinga communicative link between an AP component and a UE component.

At 620, method 600 can comprise, determining resource allocation basedon the UE data received by the selection component at 610. Determiningresource allocation can comprise applying a rule related to selection ofa resource, e.g., an AP resource, in view of characteristics of theresource requested by a UE and characteristics of a resource that isavailable via an AP. In an aspect, the rule can consider current,historical, and/or anticipated resource characteristics. Nearly anyhistorical characteristic and/or anticipated future characteristic foran AP resource can be employed in the determining resource allocation of620. Moreover historical and anticipated characteristics of UE requestedresources can be employed.

At 630, method 600 can comprise, generating an ATD that can enableselection of a UE-AP pair with regard to forming a communicative linkbetween a UE and an AP component. At this point, method 600 can end. ATDcan comprise information used to enable a UE to initiate a communicativelink with a selected AP. The communicative link with the AP can bedirected to a designated resource of the AP. The communicative link withthe AP can be responsive to requested resource characteristics that canbe indicated via UE data. In an aspect, ATD can enableresource-sensitive selection of a UE-AP pair with regard to forming acommunicative link between the UE and the AP. In some embodiments, ATDcan be received by a UE via an AP component. In other embodiments, ATDcan be received by a UE via another component, for example, ATD can becommunicated to a UE from via a carrier backbone network to the UE, etc.In an aspect, ATD can comprise UE data, in whole or in part. In someembodiments, ATD can comprise UEID information. Further, ATD cancomprise AP data, in whole or in part. Moreover, ATD can compriseinformation related to a selected UE-AP pairing. In some embodiments,ATD can comprise information related to a plurality of UE-AP pairings,which can comprise parings for a UE with different APs, parings for a UEwith different resources of an AP, parings for a plurality of UEs withdifferent APs, parings for a plurality of UEs with different resourcesof an AP, no paring for a UE with an AP or AP resource, etc. As such,ATD can be generated for one UE and one AP device, for multiple UEs andone AP device, for one UE and multiple AP devices, etc., wherein the APdevice(s) can have one or more resources, the UE(s) can be associatedwith one or more requested resource, and wherein a rule related toselecting an AP resource in response to a UE requested resource has beensatisfied.

FIG. 7 illustrates a method 700 that facilitates resource-sensitivetoken-based access point selection via a UE component in accordance withaspects of the subject disclosure. At 710, method 700 can includebroadcasting UE data from a UE component. UE data can include UEIDinformation, historical UE information, UE location information, UErequested resource information, UE state information, UE providerinformation, UE subscription plan information, UE environmentalinformation, or nearly any other type of UE related information. The UEdata can be employed with AP data to select a UE-AP pair, wherein APdata can include APID information, historical AP information, APlocation information, AP available resource information, AP stateinformation, AP carrier information, AP environmental information, ornearly any other type of AP related information. An AP can includedevices or components enabling a communicative link between an APcomponent and a UE component. Broadcasting UE data from a UE cancomprise transmitting UE data in a manner that allows an AP component toreceive the UE data. The AP component can then make some or all of theUE data available for selection of a UE-AP resource pair.

At 720, method 700 can comprise, receiving ATD that can be generated inresponse to a resource allocation determination based on the UE data. Inan aspect, the ATD can be received at the UE from another device orcomponent. As an example, AP component 110, selection component 240,etc., can generate the ATD and can make it available to be received bythe UE at 720. In some embodiments, the ATD can be received by a UE at720 via an AP component. In other embodiments, ATD can be received by aUE at 720 via another component, for example, ATD can be communicated toa UE from via a carrier backbone network to the UE, etc.

At 730, the UE can initiate a link with an AP component based on theATD. At this point, method 700 can end. The ATD received at 720 canenable selection of a UE-AP pair with regard to forming a communicativelink between a UE and an AP component wherein the ATD can compriseinformation used to enable a UE to initiate a communicative link with aselected AP. The ATD can comprise information related to establishing acommunicative link with an AP with access to a designated resource ofthe AP. As such, the communicative link with the AP can be responsive torequested resource characteristics that can be indicated via UE databroadcast at 710. In an aspect, ATD can comprise UE data from 710, inwhole or in part. In some embodiments, ATD can comprise UEIDinformation. Further, ATD can comprise AP data, in whole or in part.Moreover, ATD can comprise information related to a selected UE-APpairing. In some embodiments, ATD can comprise information related to aplurality of UE-AP pairings, which can comprise parings for a UE withdifferent APs, parings for a UE with different resources of an AP,parings for a plurality of UEs with different APs, parings for aplurality of UEs with different resources of an AP, no paring for a UEwith an AP or AP resource, etc. As such, ATD can be generated for one UEand one AP device, for multiple UEs and one AP device, for one UE andmultiple AP devices, etc., wherein the AP device(s) can have one or moreresources, the UE(s) can be associated with one or more requestedresource, and wherein a rule related to selecting an AP resource inresponse to a UE requested resource has been satisfied.

FIG. 8 illustrates a method 800 that facilitates resource-sensitiveaccess point selection for a plurality of AP components in accordancewith aspects of the subject disclosure. At 810, method 800 can includereceiving first UE data associated with a first UE component. The firstUE data can be received at a first AP component and at a second UEcomponent. At 820, method 800 can comprise, receiving second UE dataassociated with a second UE component. The second UE data can bereceived at the first AP component and at the second UE component. Thefirst and second UE data can include UEID information, historical UEinformation, UE location information, UE requested resource information,UE state information, UE provider information, UE subscription planinformation, UE environmental information, or nearly any other type ofUE related information, corresponding to the first or second UE.Generally, UE data can be employed with AP data to select a UE-AP pair,wherein AP data can include APID information, historical AP information,AP location information, AP available resource information (e.g.,currently available, anticipated available, historically available,whitelists, blacklists, etc.), AP state information, AP carrierinformation, AP environmental information, or nearly any other type ofAP related information. An AP can include devices or components enablinga communicative link between an AP component and a UE component.

At 830, method 800 can comprise, determining resource allocation forresources of the first and second AP components based on the first andsecond UE data received at 810 and 820. Determining resource allocationcan comprise applying a rule related to selection of a resource, e.g.,an AP resource associated with either first AP component or second APcomponent, in view of characteristics of a resource requested by a UE,e.g., the first or second UE, and characteristics of a resource that isavailable via an AP. In an aspect, the rule can consider current,historical, and/or anticipated resource characteristics. Nearly anyhistorical characteristic and/or anticipated future characteristic foran AP, and nearly any historical and anticipated characteristics of UErequested resources, resource can be employed in the determiningresource allocation of 830, and all such characteristics are consideredwithin the scope of the present disclosure.

At 840, method 800 can comprise, generating first token data and secondtoken data based on the resource allocation information determined at830. At this point, method 800 can end. First token data and secondtoken data can enable selection of a UE-AP pair with regard to forming acommunicative link between a UE, e.g., the first UE and/or the secondUE, and an AP component, e.g., an AP associated with the first and/orsecond AP component.

The tokens can comprise information enabling a UE to initiate acommunicative link with a selected AP. The communicative link with theAP can be directed to a designated resource of the AP. The communicativelink with the AP can be responsive to requested resource characteristicsthat can be indicated via UE data. In an aspect, token data can enableresource-sensitive selection of a UE-AP pair with regard to forming acommunicative link between the UE and the AP. In some embodiments, thefirst and/or second token data can be received by a UE via an APcomponent. In other embodiments, the first and/or second token data canbe received by a UE via another component, for example, the first tokendata can be communicated to the first UE component via a carriercore-network component, etc.

In an aspect, the first and/or second token data can comprise UE data,in whole or in part. In some embodiments, the first and/or second tokendata can comprise UEID information. Further, the first and/or secondtoken data can comprise AP data, in whole or in part. Moreover, thefirst and/or second token data can comprise information related to aselected UE-AP pairing. In some embodiments, the first and/or secondtoken data can comprise information related to a plurality of UE-APpairings, which can comprise parings for a UE with different APs,parings for a UE with different resources of an AP, parings for aplurality of UEs with different APs, parings for a plurality of UEs withdifferent resources of an AP, no paring for a UE with an AP or APresource, etc. As such, the first and/or second token data can begenerated for one UE and one AP device, for multiple UEs and one APdevice, for one UE and multiple AP devices, etc., wherein the APdevice(s) can have one or more resources, the UE(s) can be associatedwith one or more requested resource, and wherein a rule related toselecting an AP resource in response to a UE requested resource has beensatisfied. Of note, in some embodiments, where a token comprises UE-APpair information for the several UEs, e.g., the first and second UEcomponents, other tokens may not be generated, e.g., first and second UEcomponents can receive first token data having all the pairing infoneeded and, as such, second token data can be redundant and need not begenerated at 840. In other embodiments, the first and second tokens cancomprise UE-AP resource pairing info for specific UEs, e.g., first andsecond UE components respectively, such that each UE receives arespective token with pairing info specific to that UE, e.g., first UEcomponent gets first token data generated at 840, and second UEcomponent gets second token data generated at 840.

FIG. 9 is a schematic block diagram of a computing environment 900 withwhich the disclosed subject matter can interact. The system 900 includesone or more remote component(s) 910. The remote component(s) 910 can behardware and/or software (e.g., threads, processes, computing devices).In some embodiments, remote component(s) 910 can include servers,personal servers, wireless telecommunication network devices, etc. As anexample, remote component(s) 910 can be selection component 240, 340,440, nodal AP controller component 350, 450, etc.

The system 900 also includes one or more local component(s) 920. Thelocal component(s) 920 can be hardware and/or software (e.g., threads,processes, computing devices). In some embodiments, local component(s)920 can include, for example, AP component 110, 210, 310, 410, 412, 414,UE 420, 422, 424, etc.

One possible communication between a remote component(s) 910 and a localcomponent(s) 920 can be in the form of a data packet adapted to betransmitted between two or more computer processes. Another possiblecommunication between a remote component(s) 910 and a local component(s)920 can be in the form of circuit-switched data adapted to betransmitted between two or more computer processes in radio time slots.The system 900 includes a communication framework 940 that can beemployed to facilitate communications between the remote component(s)910 and the local component(s) 920, and can include an air interface,e.g., Uu interface of a UMTS network. Remote component(s) 910 can beoperably connected to one or more remote data store(s) 950, such as ahard drive, SIM card, device memory, etc., that can be employed to storeinformation on the remote component(s) 910 side of communicationframework 940. Similarly, local component(s) 920 can be operablyconnected to one or more local data store(s) 930, that can be employedto store information on the local component(s) 920 side of communicationframework 940.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 10 , and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthe disclosed subject matter also can be implemented in combination withother program modules. Generally, program modules include routines,programs, components, data structures, etc. that performs particulartasks and/or implement particular abstract data types.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It is noted that thememory components described herein can be either volatile memory ornonvolatile memory, or can include both volatile and nonvolatile memory,by way of illustration, and not limitation, volatile memory 1020 (seebelow), non-volatile memory 1022 (see below), disk storage 1024 (seebelow), and memory storage 1046 (see below). Further, nonvolatile memorycan be included in read only memory, programmable read only memory,electrically programmable read only memory, electrically erasable readonly memory, or flash memory. Volatile memory can include random accessmemory, which acts as external cache memory. By way of illustration andnot limitation, random access memory is available in many forms such assynchronous random access memory, dynamic random access memory,synchronous dynamic random access memory, double data rate synchronousdynamic random access memory, enhanced synchronous dynamic random accessmemory, Synchlink dynamic random access memory, and direct Rambus randomaccess memory. Additionally, the disclosed memory components of systemsor methods herein are intended to comprise, without being limited tocomprising, these and any other suitable types of memory.

Moreover, it is noted that the disclosed subject matter can be practicedwith other computer system configurations, including single-processor ormultiprocessor computer systems, mini-computing devices, mainframecomputers, as well as personal computers, hand-held computing devices(e.g., personal digital assistant, phone, watch, tablet computers,netbook computers, . . . ), microprocessor-based or programmableconsumer or industrial electronics, and the like. The illustratedaspects can also be practiced in distributed computing environmentswhere tasks are performed by remote processing devices that are linkedthrough a communications network; however, some if not all aspects ofthe subject disclosure can be practiced on stand-alone computers. In adistributed computing environment, program modules can be located inboth local and remote memory storage devices.

FIG. 10 illustrates a block diagram of a computing system 1000 operableto execute the disclosed systems and methods in accordance with anembodiment. Computer 1012, which can be, for example, part of selectioncomponent 240, 340, 440, nodal AP controller component 350, 450, APcomponent 110, 210, 310, 410, 510, UE 420, 422, 424, etc., includes aprocessing unit 1014, a system memory 1016, and a system bus 1018.System bus 1018 couples system components including, but not limited to,system memory 1016 to processing unit 1014. Processing unit 1014 can beany of various available processors. Dual microprocessors and othermultiprocessor architectures also can be employed as processing unit1014.

System bus 1018 can be any of several types of bus structure(s)including a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, industrial standardarchitecture, micro-channel architecture, extended industrial standardarchitecture, intelligent drive electronics, video electronics standardsassociation local bus, peripheral component interconnect, card bus,universal serial bus, advanced graphics port, personal computer memorycard international association bus, Firewire (Institute of Electricaland Electronics Engineers 1194), and small computer systems interface.

System memory 1016 can include volatile memory 1020 and nonvolatilememory 1022. A basic input/output system, containing routines totransfer information between elements within computer 1012, such asduring start-up, can be stored in nonvolatile memory 1022. By way ofillustration, and not limitation, nonvolatile memory 1022 can includeread only memory, programmable read only memory, electricallyprogrammable read only memory, electrically erasable read only memory,or flash memory. Volatile memory 1020 includes read only memory, whichacts as external cache memory. By way of illustration and notlimitation, read only memory is available in many forms such assynchronous random access memory, dynamic read only memory, synchronousdynamic read only memory, double data rate synchronous dynamic read onlymemory, enhanced synchronous dynamic read only memory, Synchlink dynamicread only memory, Rambus direct read only memory, direct Rambus dynamicread only memory, and Rambus dynamic read only memory.

Computer 1012 can also include removable/non-removable,volatile/non-volatile computer storage media. FIG. 10 illustrates, forexample, disk storage 1024. Disk storage 1024 includes, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, flash memory card, or memory stick. In addition, disk storage1024 can include storage media separately or in combination with otherstorage media including, but not limited to, an optical disk drive suchas a compact disk read only memory device, compact disk recordabledrive, compact disk rewritable drive or a digital versatile disk readonly memory. To facilitate connection of the disk storage devices 1024to system bus 1018, a removable or non-removable interface is typicallyused, such as interface 1026.

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, read only memory, programmable read only memory,electrically programmable read only memory, electrically erasable readonly memory, flash memory or other memory technology, compact disk readonly memory, digital versatile disk or other optical disk storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, or other tangible media which can be used tostore desired information. In this regard, the term “tangible” herein asmay be applied to storage, memory or computer-readable media, is to beunderstood to exclude only propagating intangible signals per se as amodifier and does not relinquish coverage of all standard storage,memory or computer-readable media that are not only propagatingintangible signals per se. In an aspect, tangible media can includenon-transitory media wherein the term “non-transitory” herein as may beapplied to storage, memory or computer-readable media, is to beunderstood to exclude only propagating transitory signals per se as amodifier and does not relinquish coverage of all standard storage,memory or computer-readable media that are not only propagatingtransitory signals per se. Computer-readable storage media can beaccessed by one or more local or remote computing devices, e.g., viaaccess requests, queries or other data retrieval protocols, for avariety of operations with respect to the information stored by themedium. As such, for example, a computer-readable medium can compriseexecutable instructions stored thereon that, in response to execution,cause a system comprising a processor to perform operations, comprising:transmitting a request for data via an air interface or other wirelessinterface to a remote device, e.g., AP component, 210, 310, 410, 412,414, etc., wherein the request is related to receiving data by thesystem, e.g., selection component 240, 340, 440, nodal AP controllercomponent 350, 450, etc., via the wireless interface, and in response tothe transmitting the request, receiving data by the system via thewireless interface from the remote device, wherein: the data wasreceived by the remote device from another device, e.g., local datastore associated with AP component, 210, 310, 410, 412, 414, etc.,associated with storing the data before being received by the system,the receipt of the data by the remote device is associated with a lowerlatency and a higher throughput than a latency and a throughput,respectively, of the wireless interface between the system and theremote device, and the data is received by the system, as a result of apush of the data by the remote device, without an additional request bythe system.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

It can be noted that FIG. 10 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment 1000. Such software includes an operating system1028. Operating system 1028, which can be stored on disk storage 1024,acts to control and allocate resources of computer system 1012. Systemapplications 1030 take advantage of the management of resources byoperating system 1028 through program modules 1032 and program data 1034stored either in system memory 1016 or on disk storage 1024. It is to benoted that the disclosed subject matter can be implemented with variousoperating systems or combinations of operating systems.

A user can enter commands or information into computer 1012 throughinput device(s) 1036. As an example, a user interface can allow entry ofuser preference information, etc., and can be embodied in a touchsensitive display panel, a mouse input GUI, a command line controlledinterface, etc., allowing a user to interact with computer 1012. Inputdevices 1036 include, but are not limited to, a pointing device such asa mouse, trackball, stylus, touch pad, keyboard, microphone, joystick,game pad, satellite dish, scanner, TV tuner card, digital camera,digital video camera, web camera, cell phone, smartphone, tabletcomputer, etc. These and other input devices connect to processing unit1014 through system bus 1018 by way of interface port(s) 1038. Interfaceport(s) 1038 include, for example, a serial port, a parallel port, agame port, a universal serial bus, an infrared port, a Bluetooth port,an IP port, or a logical port associated with a wireless service, etc.Output device(s) 1040 use some of the same type of ports as inputdevice(s) 1036.

Thus, for example, a universal serial busport can be used to provideinput to computer 1012 and to output information from computer 1012 toan output device 1040. Output adapter 1042 is provided to illustratethat there are some output devices 1040 like monitors, speakers, andprinters, among other output devices 1040, which use special adapters.Output adapters 1042 include, by way of illustration and not limitation,video and sound cards that provide means of connection between outputdevice 1040 and system bus 1018. It should be noted that other devicesand/or systems of devices provide both input and output capabilitiessuch as remote computer(s) 1044. As an example, vehicle subsystems, suchas headlights, brake lights, stereos, vehicle information sharingdevice, etc., can include an output adapter 1042 to enable use inaccordance with the presently disclosed subject matter.

Computer 1012 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1044. Remote computer(s) 1044 can be a personal computer, a server, arouter, a network PC, cloud storage, cloud service, a workstation, amicroprocessor based appliance, a peer device, or other common networknode and the like, and typically includes many or all of the elementsdescribed relative to computer 1012.

For purposes of brevity, only a memory storage device 1046 isillustrated with remote computer(s) 1044. Remote computer(s) 1044 islogically connected to computer 1012 through a network interface 1048and then physically connected by way of communication connection 1050.Network interface 1048 encompasses wire and/or wireless communicationnetworks such as local area networks and wide area networks. Local areanetwork technologies include fiber distributed data interface, copperdistributed data interface, Ethernet, Token Ring and the like. Wide areanetwork technologies include, but are not limited to, point-to-pointlinks, circuit-switching networks like integrated services digitalnetworks and variations thereon, packet switching networks, and digitalsubscriber lines. As noted below, wireless technologies may be used inaddition to or in place of the foregoing.

Communication connection(s) 1050 refer(s) to hardware/software employedto connect network interface 1048 to bus 1018. While communicationconnection 1050 is shown for illustrative clarity inside computer 1012,it can also be external to computer 1012. The hardware/software forconnection to network interface 1048 can include, for example, internaland external technologies such as modems, including regular telephonegrade modems, cable modems and digital subscriber line modems,integrated services digital network adapters, and Ethernet cards.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit, a digital signalprocessor, a field programmable gate array, a programmable logiccontroller, a complex programmable logic device, a discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Processorscan exploit nano-scale architectures such as, but not limited to,molecular and quantum-dot based transistors, switches and gates, inorder to optimize space usage or enhance performance of user equipment.A processor may also be implemented as a combination of computingprocessing units.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software or firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Further, the term “include” is intended to be employed as an open orinclusive term, rather than a closed or exclusive term. The term“include” can be substituted with the term “comprising” and is to betreated with similar scope, unless otherwise explicitly used otherwise.As an example, “a basket of fruit including an apple” is to be treatedwith the same breadth of scope as, “a basket of fruit comprising anapple.”

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point,” “base station,”“Node B,” “evolved Node B,” “eNodeB,” “home Node B,” “home accesspoint,” and the like, are utilized interchangeably in the subjectapplication, and refer to a wireless network component or appliance thatserves and receives data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream to and from a set ofsubscriber stations or provider enabled devices. Data and signalingstreams can include packetized or frame-based flows.

Additionally, the terms “core-network”, “core”, “core carrier network”,“carrier-side”, or similar terms can refer to components of atelecommunications network that typically provides some or all ofaggregation, authentication, call control and switching, charging,service invocation, or gateways. Aggregation can refer to the highestlevel of aggregation in a service provider network wherein the nextlevel in the hierarchy under the core nodes is the distribution networksand then the edge networks. UEs do not normally connect directly to thecore networks of a large service provider but can be routed to the coreby way of a switch or radio access network. Authentication can refer todeterminations regarding whether the user requesting a service from thetelecom network is authorized to do so within this network or not. Callcontrol and switching can refer determinations related to the futurecourse of a call stream across carrier equipment based on the callsignal processing. Charging can be related to the collation andprocessing of charging data generated by various network nodes. Twocommon types of charging mechanisms found in present day networks can beprepaid charging and postpaid charging. Service invocation can occurbased on some explicit action (e.g. call transfer) or implicitly (e.g.,call waiting). It is to be noted that service “execution” may or may notbe a core network functionality as third party network/nodes may takepart in actual service execution. A gateway can be present in the corenetwork to access other networks. Gateway functionality can be dependenton the type of the interface with another network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components (e.g., supportedthrough artificial intelligence, as through a capacity to makeinferences based on complex mathematical formalisms), that can providesimulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks include broadcasttechnologies (e.g., sub-Hertz, extremely low frequency, very lowfrequency, low frequency, medium frequency, high frequency, very highfrequency, ultra-high frequency, super-high frequency, terahertzbroadcasts, etc.); Ethernet; X.25; powerline-type networking, e.g.,Powerline audio video Ethernet, etc.; femtocell technology; Wi-Fi;worldwide interoperability for microwave access; enhanced general packetradio service; third generation partnership project, long termevolution; third generation partnership project universal mobiletelecommunications system; third generation partnership project 2, ultramobile broadband; high speed packet access; high speed downlink packetaccess; high speed uplink packet access; enhanced data rates for globalsystem for mobile communication evolution radio access network;universal mobile telecommunications system terrestrial radio accessnetwork; or long term evolution advanced.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methods herein.One of ordinary skill in the art may recognize that many furthercombinations and permutations of the claimed subject matter arepossible. Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. A system, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: receivinguser equipment information broadcast by a user equipment trying toaccess a network, wherein the user equipment information comprises anaccess point resource requirement of the user equipment, and wherein anaccess point device connected to the network is not visible to the userequipment; based on the user equipment information and a selection rule,determining whether to make the access point visible to the userequipment for an access to the network; and in response to determiningthat the access point is to be made visible to the user equipment,sending access point information to the user equipment to make theaccess point device visible to the user equipment for the access to thenetwork, wherein the access point device is a first access point device,and wherein receiving the user equipment information is via a secondaccess point device.
 2. The system of claim 1, wherein the access pointdevice is part of a group of access point devices comprising the secondaccess point device.
 3. The system of claim 1, wherein network equipmentassociated with a network provider comprises the processor, and whereinthe network equipment is not the access point device.
 4. The system ofclaim 1, wherein the user equipment information indicates informationselected from a group of information comprising a level of userequipment mobility information, historical network resource usageinformation associated with the user equipment, and battery conditioninformation associated with the user equipment.
 5. The system of claim1, wherein the user equipment information indicates a network resourcecharacteristic of a network resource sought by the user equipment vianetwork equipment, and wherein the network resource characteristicfacilitates selection of the network resource.
 6. The system of claim 5,wherein the network resource characteristic indicates a network resourceminimum performance characteristic.
 7. The system of claim 5, whereinthe network resource characteristic indicates a network resource idealperformance characteristic.
 8. The system of claim 1, wherein the userequipment information indicates subscription plan informationcorresponding to the user equipment.
 9. A non-transitorymachine-readable medium, comprising executable instructions that, whenexecuted by a processor of a system, facilitate performance ofoperations, comprising: receiving user equipment information broadcastby a user equipment trying to connect to a network, wherein the userequipment information comprises preferred access point linkcharacteristics for an access point link to be provisioned for the userequipment, and wherein an access point device operating on the networkis unidentifiable by the user equipment for connecting to the network;determining whether the user equipment information satisfies a selectionrule related to the access point device being enabled to be identifiableby the user equipment for connecting to the network; and in response todetermining that the user equipment information satisfies the selectionrule, communicating access point information to the user equipment toenable the user equipment to identify the access point device, whereinthe access point device is a first access point device, and whereinreceiving the user equipment information is via a second access pointdevice.
 10. The non-transitory machine-readable medium of claim 9,wherein network equipment associated with a network provider identitycomprises the processor.
 11. The non-transitory machine-readable mediumof claim 9, wherein the access point device is part of a group of accesspoint devices comprising the second access point device.
 12. Thenon-transitory machine-readable medium of claim 9, wherein receiving theuser equipment information via the second access point devicefacilitates handing over the user equipment to the first access pointdevice.
 13. The non-transitory machine-readable medium of claim 9,wherein the user equipment information indicates subscription planinformation corresponding to the user equipment.
 14. The non-transitorymachine-readable medium of claim 9, wherein the preferred access pointlink characteristics indicate a minimum performance characteristic forthe access point link.
 15. A method, comprising: receiving, by a systemcomprising a processor, user equipment information broadcast by a userequipment for establishing a connection to a network, wherein the userequipment information identifies a resource requirement, and wherein theuser equipment does not have knowledge of an access point deviceconnected to the network at a time that the user equipment informationwas broadcast; determining whether the user equipment informationsatisfies a selection rule related to the access point device applicableto providing the user equipment with the knowledge of the access pointdevice; and in response to determining that the user equipmentinformation satisfies the selection rule, sending access pointinformation to the user equipment that comprises the knowledge of theaccess point device, wherein the access point device is a first accesspoint device, and wherein receiving the user equipment information isvia a second access point device.
 16. The method of claim 15, furthercomprising enabling, by the system, a transfer of a network connectionassociated with the user equipment to the first access point device inresponse to the user equipment information being received via the secondaccess point device.
 17. The method of claim 15, wherein the resourcerequirement indicates a minimum performance characteristic for theconnection.
 18. The method of claim 15, wherein the resource requirementindicates a target performance characteristic for the connection. 19.The method of claim 15, wherein the resource requirement indicates asecurity characteristic for the connection.
 20. The method of claim 15,wherein the user equipment information indicates subscription planinformation corresponding to the user equipment.